home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Monster Media 1994 #2
/
Monster Media No. 2 (Monster Media)(1994).ISO
/
pcboard
/
sat114.zip
/
CONFIG.DOC
< prev
next >
Wrap
Text File
|
1994-05-31
|
4KB
|
104 lines
╓─────────────────────────────────────────────────────────────────────────────╖
║ ░░░░░ PPSS Series Configuration Information ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ ║
╙─────────────────────────────────────────────────────────────────────────────╜
All PCBoard Professional Sysop Series (PPSS) programs and packages operate
out of a unified configuration file called PPSS.CFG, the format of
which is discussed below.
The PPSS.CFG file is automatically created and/or added to as a program is
run for the first time. The PPSS.CFG file can be specified on the command
line, the environment, the current directory, or in the DOS path.
To specify the PPSS.CFG on the command line, use the keyword
parameter PPSSCFG, i.e.
PROGRAM CFG=C:\WORK\PPSS.CFG
To specify the PPSS.CFG in the environment, use the PPSSCFG variable, i.e.
SET PPSSCFG=C:\WORK\PPSS.CFG
If you get an "Out of environment space" message, consult your DOS manual
for information on increasing your DOS environment space. The SET statement
is best placed in your AUTOEXEC.BAT file so it will automatically load
whenever you reboot or turn on your machine.
In order of search for the PPSS.CFG file, PPSS programs will first use a
provided command line argument, then the environment, then the current
directory, then the DOS Path.
╓─────────────────────────────────────────────────────────────────────────────╖
║ ░░░░░ PPSS.CFG Format ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ ║
╙─────────────────────────────────────────────────────────────────────────────╜
The PPSS.CFG file has a general configuration area denoted by the marker
"[General Configuration]" which supplies general configuration items such as
Version, BBSName, SysopName, PCBDir, PKZip, and TextEditor.
Program configuration areas are used to specify items for a particular
program such as Registration, Version and WarningLevel.
SAMPLE FORMAT
column 1 --+
V
; This is a comment
[General Configuration]
Version=100
BBSName=Your BBS Name Here
SysopName=Your Name
PCBDir=C:\P
PKZIP=C:\UTIL\PKZIP.EXE
PKUNZIP=C:\UTIL\PKUNZIP.EXE
TextEditor=C:\UTIL\Q.EXE
[Message Base Check]
Version=100
VerifyLevel=1
ErrorLevel=1
The PPSS.CFG file can be edited using any text editor. If you use an
editor that inserts control codes, be sure to save in "plain text"
format.
- The order of areas within PPSS.CFG is also not important.
- The order of parameters within an area is not important.
- Parameter keywords and area titles are case-insensitive.
- Blank lines are ignored.
- Comments start with a semi-colon (';') in column one.
- All area titles and parameters should begin in column one.
- There should be no spaces between a keyword and the '=' sign,
and no spaces between the '=' sign and the parameter.
The sole exception is certain text items such as report titles.
╓─────────────────────────────────────────────────────────────────────────────╖
║ ░░░░░ Command Line Overrides ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ ║
╙─────────────────────────────────────────────────────────────────────────────╜
Many PPSS program parameters can be overridden at run time via the command
line. Typically, a program will allow both long (keyword) and short
(character)parameter overrides and the use of either or neither of '-' and
'/' as short parameter markers. Check the individual program documentation
for specifics on allowed overrides for each program. Keyword indicators are
not case-sensitive. Character indicators may be case-sensitive on a
program-by-program basis but usually are not.
Examples:
PROGRAM VERIFYLEVEL=1 WARNINGLEVEL=1
PROGRAM WarningLevel=1 VerifyLevel=1
PROGRAM /V1 /W1
PROGRAM -W1 -v1
PROGRAM w1 v1
Since all command line parameter overrides are keyword or character
flagged, order is not important.